Relaxation of mobility condition based on serving cell quality

ABSTRACT

A method and apparatus for relaxation of mobility condition based on serving cell quality is provided. A wireless device, which has been configured with conditional mobility, performs a conditional mobility to a target cell by using a mobility condition related to the target cell upon detecting a radio link problem on a serving cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

Pursuant to 35 U.S.C. § 119 (e), this application claims the benefit of Korean Patent Applications No. 10-2019-0022713 filed on Feb. 26, 2019, and No. 10-2019-0022706 filed on Feb. 26, 2019, the contents of which are all hereby incorporated by reference herein in their entirety.

TECHNICAL FIELD

The present disclosure relates to relaxation of mobility condition based on serving cell quality.

BACKGROUND

3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible.

It is suggested to consider handover procedure based on a configured condition (i.e., conditional handover (CHO)). The motivation for the handover procedure based on a configured condition is to reduce the time to taken for transmission of measurement reporting and reception of handover command and handover preparation so that it would be possible to reduce the handover failure caused by not receiving handover command at a proper time.

SUMMARY

While performing conditional handover, i.e., before completing actual handover to a target cell, a serving cell problem may happen. In this case, it may be better to perform handover to the target cell due to the serving cell problem. This issued should be addressed.

In an aspect, a method for a wireless device in a wireless communication system is provided. The method includes receiving information for a conditional mobility condition related to a target cell, detecting a radio link problem on a serving cell, and performing a conditional mobility to the target cell by using a mobility condition related to the target cell upon detecting the radio link problem on the serving cell.

In another aspect, an apparatus for implementing the above method is provided.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

FIG. 10 shows an example of SSB to which implementations of the present disclosure is applied.

FIG. 11 shows an example of SI acquisition procedure to which implementations of the present disclosure is applied.

FIG. 12 shows an example of contention-based random access (CBRA) to which implementations of the present disclosure is applied.

FIG. 13 shows an example of contention-free random access (CFRA) to which implementations of the present disclosure is applied.

FIG. 14 shows a concept of threshold of the SSB for RACH resource association to which implementations of the present disclosure is applied.

FIG. 15 shows an example of operation of power ramping counter to which implementations of the present disclosure is applied.

FIG. 16 shows an example of inter-gNB handover procedures to which implementations of the present disclosure is applied.

FIG. 17 shows an example of overall procedure for condition based autonomous handover procedure to which implementations of the present disclosure is applied.

FIG. 18 shows an example of a method for a wireless device to which implementations of the present disclosure is applied.

FIG. 19 show an example of a method for UE to perform conditional mobility to which implementations of the present disclosure is applied.

DETAILED DESCRIPTION

The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.

For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

In the present disclosure, “A or B” may mean “only A”, “only B”, or “both A and B”.

In other words, “A or B” in the present disclosure may be interpreted as “A and/or B”. For example, “A, B or C” in the present disclosure may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”.

In the present disclosure, slash (/) or comma (,) may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B or C”.

In the present disclosure, “at least one of A and B” may mean “only A”, “only B” or “both A and B”. In addition, the expression “at least one of A or B” or “at least one of A and/or B” in the present disclosure may be interpreted as same as “at least one of A and B”.

In addition, in the present disclosure, “at least one of A, B and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. In addition, “at least one of A, B or C” or “at least one of A, B and/or C” may mean “at least one of A, B and C”.

Also, parentheses used in the present disclosure may mean “for example”. In detail, when it is shown as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” in the present disclosure is not limited to “PDCCH”, and “PDDCH” may be proposed as an example of “control information”. In addition, even when shown as “control information (i.e., PDCCH)”, “PDCCH” may be proposed as an example of “control information”.

Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and/or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and/or connection (e.g., 5G) between devices.

Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and/or descriptions may refer to the same and/or corresponding hardware blocks, software blocks, and/or functional blocks unless otherwise indicated.

FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1 .

Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).

Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable method.

eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality. Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application program using data connection provided by a communication system. Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate. A streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet. These many application programs require connectivity of an always turned-on state in order to push real-time information and alarm for users. Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment. The cloud storage is a special use case which accelerates growth of uplink data transmission rate. 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience. Entertainment, for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane. Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.

In addition, one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.

URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable/available low-latency link such as a self-driving vehicle. A level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.

5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. A specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.

Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds. Another use case of an automotive field is an AR dashboard. The AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident. The next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify. Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.

A smart city and a smart home/building mentioned as a smart society will be embedded in a high-density wireless sensor network. A distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.

Consumption and distribution of energy including heat or gas is distributed at a higher level so that automated control of the distribution sensor network is demanded. The smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation. The smart grid may also be regarded as another sensor network having low latency.

Mission critical application (e.g., e-health) is one of 5G use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communication gradually becomes important in the field of an industrial application. Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.

Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system. The use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.

Referring to FIG. 1 , the communication system 1 includes wireless devices 100 a to 100 f, base stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS/network node with respect to other wireless devices.

The wireless devices 100 a to 100 f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication/radio/5G devices. The wireless devices 100 a to 100 f may include, without being limited to, a robot 100 a, vehicles 100 b-1 and 100 b-2, an extended reality (XR) device 100 c, a hand-held device 100 d, a home appliance 100 e, an IoT device 100 f, and an artificial intelligence (AI) device/server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR/VR/Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

In the present disclosure, the wireless devices 100 a to 100 f may be called user equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather/environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

The UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard.

The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.

The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.

The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.

The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.

The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system.

The weather/environment device may include, for example, a device for monitoring or predicting a weather/environment.

The wireless devices 100 a to 100 f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100 a to 100 f and the wireless devices 100 a to 100 f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100 a to 100 f may communicate with each other through the BSs 200/network 300, the wireless devices 100 a to 100 f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200/network 300. For example, the vehicles 100 b-1 and 100 b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100 a to 100 f.

Wireless communication/connections 150 a, 150 b and 150 c may be established between the wireless devices 100 a to 100 f and/or between wireless device 100 a to 100 f and BS 200 and/or between BSs 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150 a, sidelink communication (or device-to-device (D2D) communication) 150 b, inter-base station communication 150 c (e.g., relay, integrated access and backhaul (JAB)), etc. The wireless devices 100 a to 100 f and the BSs 200/the wireless devices 100 a to 100 f may transmit/receive radio signals to/from each other through the wireless communication/connections 150 a, 150 b and 150 c. For example, the wireless communication/connections 150 a, 150 b and 150 c may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

Referring to FIG. 2 , a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR). In FIG. 2 , {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100 a to 100 f and the BS 200}, {the wireless device 100 a to 100 f and the wireless device 100 a to 100 f} and/or {the BS 200 and the BS 200} of FIG. 1 .

The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver(s) 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the second wireless device 200 may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.

The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

The one or more transceivers 106 and 206 may convert received radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters. For example, the transceivers 106 and 206 can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and/or filters under the control of the processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the transceivers 102 and 202.

In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be configured to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be configured to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 1 ).

Referring to FIG. 3 , wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and/or the one or more memories 104 and 204 of FIG. 2 . For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG. 2 and/or the one or more antennas 108 and 208 of FIG. 2 . The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric/mechanical operation of each of the wireless devices 100 and 200 based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100 a of FIG. 1 ), the vehicles (100 b-1 and 100 b-2 of FIG. 1 ), the XR device (100 c of FIG. 1 ), the hand-held device (100 d of FIG. 1 ), the home appliance (100 e of FIG. 1 ), the IoT device (100 f of FIG. 1 ), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 1 ), the BSs (200 of FIG. 1 ), a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed place according to a use—example/service.

In FIG. 3 , the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

Referring to FIG. 4 , wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.

The first wireless device 100 may include at least one transceiver, such as a transceiver 106, and at least one processing chip, such as a processing chip 101. The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and/or instructions. The memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may control the processor 102 to perform one or more protocols. For example, the software code 105 may control the processor 102 may perform one or more layers of the radio interface protocol.

The second wireless device 200 may include at least one transceiver, such as a transceiver 206, and at least one processing chip, such as a processing chip 201. The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and/or instructions. The memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 may perform one or more layers of the radio interface protocol.

FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

Referring to FIG. 5 , a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the first wireless device 100 of FIG. 4 .

A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 1112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.

The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and/or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or a corresponding next generation processor.

The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and/or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

The transceiver 106 is operatively coupled with the processor 102, and transmits and/or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and/or receive a radio signal.

The power management module 110 manages power for the processor 102 and/or the transceiver 106. The battery 112 supplies power to the power management module 110.

The display 114 outputs results processed by the processor 102. The keypad 116 receives inputs to be used by the processor 102. The keypad 16 may be shown on the display 114.

The SIM card 118 is an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards.

The speaker 120 outputs sound-related results processed by the processor 102. The microphone 122 receives sound-related inputs to be used by the processor 102.

FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

In particular, FIG. 6 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 7 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 6 , the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 7 , the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a non-access stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an access stratum (AS).

In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network quality of service (QoS) flows.

In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing/de-multiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and/or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.

In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to/from NAS from/to UE.

FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

The frame structure shown in FIG. 8 is purely exemplary and the number of subframes, the number of slots, and/or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

Referring to FIG. 8 , downlink and uplink transmissions are organized into frames. Each frame has T_(f)=10 ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5 ms duration. Each half-frame consists of 5 subframes, where the duration T_(sf) per subframe is 1 ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing Δf=2^(u)*15 kHz.

Table 1 shows the number of OFDM symbols per slot N^(slot) _(symb), the number of slots per frame N^(frame,u) _(slot), and the number of slots per subframe N^(subframe,u) _(slot) for the normal CP, according to the subcarrier spacing Δf=2^(u)*15 kHz.

TABLE 1 u N^(slot) _(symb) N^(frame, u) _(slot) N^(subframe, u) _(slot) 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

Table 2 shows the number of OFDM symbols per slot N^(slot) _(symb), the number of slots per frame N^(frame,u) _(slot), and the number of slots per subframe N^(subframe,u) _(slot), for the extended CP, according to the subcarrier spacing Δf=2^(u)*15 kHz.

TABLE 2 u N^(slot) _(symb) N^(frame, u) _(slot) N^(subframe, u) _(slot) 2 12 40 4

A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid of N^(size,u) _(grid,x)*N^(RB) _(sc) subcarriers and N^(subframe,u) _(symb) OFDM symbols is defined, starting at common resource block (CRB) N^(start,u) _(grid) indicated by higher-layer signaling (e.g., RRC signaling), where N^(size,u) _(grid,x) is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. N^(RB) _(sc) is the number of subcarriers per RB. In the 3GPP based wireless communication system, N^(RB) _(sc) is 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth N^(size,u) _(grid) for subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with ‘point A’ which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 to N^(size) _(BWP,i)−1, where i is the number of the bandwidth part. The relation between the physical resource block n_(PRB) in the bandwidth part i and the common resource block n_(CRB) is as follows: n_(PRB)=n_(CRB)+N^(size) _(BWP,i), where N^(size) _(BWP,i) is the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 3 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean “sub 6 GHz range”, FR2 may mean “above 6 GHz range,” and may be referred to as millimeter wave (mmW).

TABLE 3 Frequency Range Corresponding frequency designation range Subcarrier Spacing FR1  450 MHz-6000 MHz  15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

TABLE 4 Frequency Range Corresponding frequency designation range Subcarrier Spacing FR1  410 MHz-7125 MHz  15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

In the present disclosure, the term “cell” may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A “cell” as a geographic area may be understood as coverage within which a node can provide service using a carrier and a “cell” as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The “cell” associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the “cell” of radio resources used by the node. Accordingly, the term “cell” may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA/DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA/DC, the term “serving cells” is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

Referring to FIG. 9 , “RB” denotes a radio bearer, and “H” denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted/received using radio resources through the PHY layer to/from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels physical uplink shared channel (PUSCH) and physical random access channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to physical downlink shared channel (PDSCH), physical broadcast channel (PBCH) and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to physical uplink control channel (PUCCH), and downlink control information (DCI) is mapped to physical downlink control channel (PDCCH). A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the cell ID of that cell. NR cell search is based on the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and PBCH demodulation reference signal (DM-RS), located on the synchronization raster.

The cell search procedure of the UE can be summarized in Table 5.

TABLE 5 Type of Signals Operations 1^(st) step PSS SS/PBCH block (SSB) symbol timing acquisition Cell ID detection within a cell ID group (3 hypothesis) 2^(nd) Step SSS Cell ID group detection (336 hypothesis) 3^(rd) Step PBCH DM-RS SSB index and Half frame index (Slot and frame boundary detection) 4^(th) Step PBCH Time information (80 ms, SFN, SSB index, HF) RMSI CORESET/Search space configuration 5^(th) Step PDCCH and PDSCH Cell access information RACH configuration

FIG. 10 shows an example of SSB to which implementations of the present disclosure is applied.

The SSB consists of PSS and SSS, each occupying 1 symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS. The possible time locations of SSBs within a half-frame are determined by subcarrier spacing and the periodicity of the half-frames where SSBs are transmitted is configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different beams, spanning the coverage area of a cell).

Within the frequency span of a carrier, multiple SSBs can be transmitted. The physical cell IDs (PCIs) of SSBs transmitted in different frequency locations do not have to be unique, i.e., different SSBs in the frequency domain can have different PCIs. However, when an SSB is associated with a remaining minimum system information (RMSI), the SSB corresponds to an individual cell, which has a unique NR cell global identity (NCGI). Such an SSB is referred to as a cell-defining SSB (CD-SSB). A PCell is always associated to a CD-SSB located on the synchronization raster.

Polar coding is used for PBCH.

The UE may assume a band-specific subcarrier spacing for the SSB unless a network has configured the UE to assume a different sub-carrier spacing.

PBCH symbols carry its own frequency-multiplexed DM-RS.

Quadrature phase shift keying (QPSK) modulation is used for PBCH.

System information (SI) consists of a master information block (MIB) and a number of system information blocks (SIBs), which are divided into minimum SI and other SI.

(1) Minimum SI comprises basic information required for initial access and information for acquiring any other SI. Minimum SI consists of:

-   -   MIB contains cell barred status information and essential         physical layer information of the cell required to receive         further system information (e.g., SIB1), e.g. CORESET #0         configuration. MIB is always periodically broadcast on BCH with         a periodicity of 80 ms and repetitions made within 80 ms. The         first transmission of the MIB is scheduled in subframes as         defined above for SS/PBCH block and repetitions are scheduled         according to the period of SSB.     -   SIB1 defines the availability and the scheduling of other system         information blocks (e.g., mapping of SIBs to SI message,         periodicity, SI-window size) with an indication whether one or         more SIBs are only provided on-demand and, in that case, the         configuration needed by the UE to perform the SI request and         contains information required for initial access. SIB1 is also         referred to as RMSI and is periodically broadcast on DL-SCH or         sent in a dedicated manner on DL-SCH to UEs in RRC_CONNECTED,         with a periodicity of 160 ms and variable transmission         repetition periodicity within 160 ms. The default transmission         repetition periodicity of SIB1 is 20 ms but the actual         transmission repetition periodicity is up to network         implementation. For SSB and CORESET multiplexing pattern 1, SIB1         repetition transmission period is 20 ms. For SSB and CORESET         multiplexing pattern 2/3, SIB1 transmission repetition period is         the same as the SSB period. SIB1 is cell-specific SIB.

(2) Other SI encompasses all SIBs not broadcast in the minimum SI. Those SIBs can either be periodically broadcast on DL-SCH, broadcast on-demand on DL-SCH (i.e., upon request from UEs in RRC_IDLE or RRC_INACTIVE), or sent in a dedicated manner on DL-SCH to UEs in RRC_CONNECTED. SIBs in other SI are carried in SystemInformation (SI) messages. Only SIBs having the same periodicity can be mapped to the same SI message. Each SI message is transmitted within periodically occurring time domain windows (referred to as SI-windows with same length for all SI messages). Each SI message is associated with an SI-window and the SI-windows of different SI messages do not overlap. That is, within one SI-window only the corresponding SI message is transmitted. An SI message may be transmitted a number of times within the SI-window. Any SIB except SIB1 can be configured to be cell specific or area specific, using an indication in SIB1. The cell specific SIB is applicable only within a cell that provides the SIB while the area specific SIB is applicable within an area referred to as SI area, which consists of one or several cells and is identified by systemInformationAreaID. Other SI consists of:

-   -   SIB2 contains cell re-selection information, mainly related to         the serving cell;     -   SIB3 contains information about the serving frequency and         intra-frequency neighbouring cells relevant for cell         re-selection (including cell re-selection parameters common for         a frequency as well as cell specific re-selection parameters);     -   SIB4 contains information about other NR frequencies and         inter-frequency neighbouring cells relevant for cell         re-selection (including cell re-selection parameters common for         a frequency as well as cell specific re-selection parameters);     -   SIB5 contains information about E-UTRA frequencies and E-UTRA         neighbouring cells relevant for cell re-selection (including         cell re-selection parameters common for a frequency as well as         cell specific re-selection parameters);     -   SIB6 contains an earthquake and tsunami warning system (ETWS)         primary notification;     -   SIB7 contains an ETWS secondary notification;     -   SIB8 contains a commercial mobile alert system (CMAS) warning         notification;     -   SIB9 contains information related to global positioning system         (GPS) time and coordinated universal Time (UTC).

For a UE in RRC_CONNECTED, the network can provide system information through dedicated signaling using the RRCReconfiguration message, e.g. if the UE has an active BWP with no common search space configured to monitor system information or paging.

For PSCell and SCells, the network provides the required SI by dedicated signaling, i.e., within an RRCReconfiguration message. Nevertheless, the UE shall acquire MIB of the PSCell to get system frame number (SFN) timing of the SCG (which may be different from MCG). Upon change of relevant SI for SCell, the network releases and adds the concerned SCell. For PSCell, the required SI can only be changed with Reconfiguration with Sync.

The physical layer imposes a limit to the maximum size a SIB can take. The maximum SIB1 or SI message size is 2976 bits.

FIG. 11 shows an example of SI acquisition procedure to which implementations of the present disclosure is applied.

The UE applies the SI acquisition procedure to acquire the AS and NAS information. The procedure applies to UEs in RRC_IDLE, in RRC_INACTIVE and in RRC_CONNECTED.

The UE in RRC_IDLE and RRC_INACTIVE shall ensure having a valid version of (at least) the MIB, SIB1 through SIB4 and SIB5 (if the UE supports E-UTRA).

For a cell/frequency that is considered for camping by the UE, the UE is not required to acquire the contents of the minimum SI of that cell/frequency from another cell/frequency layer. This does not preclude the case that the UE applies stored SI from previously visited cell(s).

If the UE cannot determine the full contents of the minimum SI of a cell by receiving from that cell, the UE shall consider that cell as barred.

In case of bandwidth adaptation (BA), the UE only acquires SI on the active BWP.

For UEs in RRC_IDLE and RRC_INACTIVE, a request for other SI triggers a random access procedure where MSG3 includes the SI request message unless the requested SI is associated to a subset of the PRACH resources, in which case MSG1 is used for indication of the requested other SI. When MSG1 is used, the minimum granularity of the request is one SI message (i.e., a set of SIBs), one RACH preamble and/or PRACH resource can be used to request multiple SI messages and the gNB acknowledges the request in MSG2. When MSG3 is used, the gNB acknowledges the request in MSG4.

The other SI may be broadcast at a configurable periodicity and for a certain duration. The other SI may also be broadcast when it is requested by UE in RRC_IDLE/RRC_INACTIVE.

For a UE to be allowed to camp on a cell it must have acquired the contents of the minimum SI from that cell. There may be cells in the system that do not broadcast the minimum SI and where the UE therefore cannot camp.

Change of system information (other than for ETWS/CMAS4) only occurs at specific radio frames, i.e., the concept of a modification period is used. System information may be transmitted a number of times with the same content within a modification period, as defined by its scheduling. The modification period is configured by system information.

When the network changes (some of the) system information, it first notifies the UEs about this change, i.e., this may be done throughout a modification period. In the next modification period, the network transmits the updated system information. Upon receiving a change notification, the UE acquires the new system information from the start of the next modification period. The UE applies the previously acquired system information until the UE acquires the new system information.

The random access procedure of the UE can be summarized in Table 6.

TABLE 6 Type of Signals Operations/Information Acquired 1^(st) step PRACH preamble in Initial beam acquisition UL Random election of RA-preamble ID 2^(nd) Step Random Access Timing alignment information Response on DL-SCH RA-preamble ID Initial UL grant, Temporary C-RNTI 3^(rd) Step UL transmission on RRC connection request UL-SCH UE identifier 4^(th) Step Contention Resolution Temporary C-RNTI on PDCCH for on DL initial access C-RNTI on PDCCH for UE in RRC_CONNECTED

The random access procedure is triggered by a number of events:

-   -   Initial access from RRC_IDLE;     -   RRC connection re-establishment procedure;     -   DL or UL data arrival during RRC_CONNECTED when UL         synchronization status is “non-synchronized”;     -   UL data arrival during RRC_CONNECTED when there are no PUCCH         resources for scheduling request (SR) available;     -   SR failure;     -   Request by RRC upon synchronous reconfiguration (e.g.,         handover);     -   Transition from RRC_INACTIVE;     -   To establish time alignment for a secondary timing advance group         (TAG);     -   Request for other SI;     -   Beam failure recovery.

FIG. 12 shows an example of contention-based random access (CBRA) to which implementations of the present disclosure is applied. FIG. 13 shows an example of contention-free random access (CFRA) to which implementations of the present disclosure is applied.

For random access in a cell configured with supplementary UL (SUL), the network can explicitly signal which carrier to use (UL or SUL). Otherwise, the UE selects the SUL carrier if and only if the measured quality of the DL is lower than a broadcast threshold. Once started, all uplink transmissions of the random access procedure remain on the selected carrier.

When CA is configured, the first three steps of CBRA always occur on the PCell while contention resolution (step 4) can be cross-scheduled by the PCell. The three steps of a CFRA started on the PCell remain on the PCell. CFRA on SCell can only be initiated by the gNB to establish timing advance for a secondary TAG: the procedure is initiated by the gNB with a PDCCH order (step 0) that is sent on a scheduling cell of an activated SCell of the secondary TAG, preamble transmission (step 1) takes place on the indicated SCell, and random access response (step 2) takes place on PCell.

Random access preamble sequences, of two different lengths are supported. Long sequence length 839 is applied with subcarrier spacings of 1.25 and 5 kHz and short sequence length 139 is applied with subcarrier spacings of 15, 30, 60 and 120 kHz. Long sequences support unrestricted sets and restricted sets of Type A and Type B, while short sequences support unrestricted sets only.

Multiple PRACH preamble formats are defined with one or more PRACH OFDM symbols, and different cyclic prefix and guard time. The PRACH preamble configuration to use is provided to the UE in the system information.

The UE calculates the PRACH transmit power for the retransmission of the preamble based on the most recent estimate pathloss and power ramping counter.

FIG. 14 shows a concept of threshold of the SSB for RACH resource association to which implementations of the present disclosure is applied.

The system information provides information for the UE to determine the association between the SSB and the RACH resources. The reference signal received power (RSRP) threshold for SSB selection for RACH resource association is configurable by network.

FIG. 15 shows an example of operation of power ramping counter to which implementations of the present disclosure is applied.

If the UE conducts beam switching, the counter of power ramping remains unchanged. For example, the UE may perform power ramping for retransmission of the random access preamble based on a power ramping counter. However, the power ramping counter remains unchanged if a UE conducts beam switching in the PRACH retransmissions. Referring to FIG. 15 , the UE may increase the power ramping counter by 1, when the UE retransmit the random access preamble for the same beam. However, when the beam had been changed, the power ramping counter remains unchanged.

Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell level mobility and beam level mobility.

Cell level mobility requires explicit RRC signaling to be triggered, i.e., handover.

FIG. 16 shows an example of inter-gNB handover procedures to which implementations of the present disclosure is applied.

For inter-gNB handover, the signaling procedures consist of at least the following elemental components shown in FIG. 16 .

In step S1600, the source gNB initiates handover and issues a Handover Request over the Xn interface.

In step S1610, the target gNB performs admission control. In step S1620, the target gNB provides the RRC configuration as part of the Handover Acknowledgement.

In step S1630, the source gNB provides the RRC configuration to the UE in the Handover Command. The Handover Command message includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in the Handover Command message. The access information to the target cell may include beam specific information, if any.

In step S1640, the UE moves the RRC connection to the target gNB. In step S1650, the UE replies the Handover Complete.

User data can also be sent in step S1650 if the grant allows.

The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC. RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode and for SRBs, PDCP can either be re-established together with a security key change or remain as it is without a key change.

Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB uses the same DRB configuration as the source gNB.

Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for recovering from handover failure.

Beam level mobility does not require explicit RRC signaling to be triggered. The gNB provides via RRC signaling the UE with measurement configuration containing configurations of SSB/channel state information (CSI) resources and resource sets, reports and trigger states for triggering channel and interference measurements and reports. Beam level mobility is then dealt with at lower layers by means of physical layer and MAC layer control signaling, and RRC is not required to know which beam is being used at a given point in time.

SSB-based beam level mobility is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWPs and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, beam level mobility can only be performed based on CSI-RS.

It is expected that channel conditions in NR changes rapidly considering especially in beamforming system in high frequencies. This would put obstacles in UE performing RRC level handover procedures. Compared to LTE handover performance, higher handover performance degradation is also observed. Such degradation should be addressed.

As a way to resolve the above difficulties in NR radio condition, it is suggested to consider handover procedure based on a configured condition (i.e., conditional handover (CHO)). The motivation for the handover procedure based on a configured condition is to reduce the time to taken for transmission of measurement reporting and reception of handover command and handover preparation so that it would be possible to reduce the handover failure caused by not receiving handover command at a proper time.

FIG. 17 shows an example of overall procedure for condition based autonomous handover procedure to which implementations of the present disclosure is applied.

In step S1700, the source gNB may provide measurement control information to the UE. In step S1710, the UE may transmit measurements reports based on the measurement control information.

In step S1720, the source gNB may prepare condition based autonomous handover procedure with candidate cells (e.g., Cell1 and Cell2 in FIG. 17 ). In step S1730, the source gNB provides handover assistance information to the UE.

The UE is provided with handover assistance information which includes set of candidate cells and conditions (e.g., RSRP) for handover. It may be possible the network prepares the candidate cells and provide the handover assistance information without the measurement report from the UE if the network is able to know the trajectory or location of the UE based on, e.g., location reporting. Additionally, the network may determine the set of candidate cells based on the received measurement report.

There may be a concern on signaling overhead due to earlier triggering threshold. Measurement reporting may be reduced if an approach similar to blacklisted cells is introduced. In other words, if the UE reports on one cell, the network may prepare the multiple cells which is in proximity of the reported cell and provide the list of cells which are prepared. Then, the UE may not report on the cells even if the condition for measurement reporting is triggered.

The handover assistance information may be cell quality based conditions and the configuration which may be used in a target cell. The handover assistance information may include configuration for one or more candidate cells.

In step S1740, if the UE receives the handover assistance information, the UE initiates to evaluate the conditions for the candidate cell list to determine whether to perform handover procedure to one of the candidate cells.

In step S1750, if the condition is met, the UE performs connecting to the prepared target cell.

For this procedure, since the source gNB may not know the exact timing of UE detaching from the source gNB, there may be some unnecessary downlink transmissions from the network to the UE. To address this issue, the target gNB may indicate to source gNB that the UE has completed handover successfully so that the source gNB does not transmit to the UE anymore. In addition, if the source gNB does not receive the response for the transmitted data, the source gNB may not transmit the data in downlink considering the handover situation.

As s reserving the resource in one or more candidate cell is burdensome to the network, it may be possible for the network to manage the configuration efficiently. For instance, based on the timer associated with validity of the handover assistance information, the network and UE may discard the configuration associated with the conditional handover. In addition, based on measurement report from the UE, network may configure, modify and/or discard the configuration.

Furthermore, if the UE successfully connects to the target cell, the target cell may inform to the source cell to discard the reserved configuration of the other candidate cell.

The make-before-break (MBB) and RACH-less handover are considered to reduce handover interruption in LTE. For example, MBB retains the link of source cell during handover procedure. The source cell transmits data to UE continuously until the handover is completed, so the interruption may be reduced. However, the channel quality of source cell is getting worse quickly specially in high frequency and the stopping point of data transmission between source cell and UE is not cleared, so the UE may not receive the data from the source cell or source cell may stop transmitting data early to UE when MBB is used. It can cause loss of data and handover interruption. In addition, The RACH-less handover contains UL grant for handover complete message in mobility control information via RRC Connection Reconfiguration message. It can help to skip the RACH procedure and reduce the interruption. However, RACH-less handover is only used for time aligned target cell that UE reuse the TA value. Moreover, in NR, the UL grant for target cell is required to consider beam forming. The received UL grant for target cell would not be suitable when the actual handover is performed. Therefore, it is hard to achieve Oms interruption with only applying MBB and RACH-less handover.

To achieve the Oms interruption handover, dual connectivity (DC) based handover is considered. The sequence of Oms interruption handover with single cell is regarded as following steps.

Step1: UE sends measurement report to the source gNB.

Step2: UE receives reconfiguration for adding target cell as SCG PSCell.

Step3 (Optional): UE sends measurement report to the master gNB.

Step4: UE receives role change request via reconfiguration message. The source cell becomes secondary gNB and the target cell becomes master gNB.

Step5: UE may receive a message to release SgNB.

From the above sequence, role change is performed after UE reported measurement reports. According to the timing of measurement reports, several issues can be considered.

At first, if UE reports the measurement reports when serving cell is lower than target cell or a threshold, MgNB is likely to be dropped before the role change. Especially, NR considers high frequency and beam forming. The channel quality of high frequency cell is attenuated quickly. When gNB of high frequency cell sends role change request message and receives role change acknowledge message, radio link failure (RLF) may be already occurred. So, the target cell may need to be added earlier and role change should be performed quickly. However, sending role change request and receiving role change acknowledge message is required for the role change.

On the other hand, if UE reports the measurement reports when target cell is higher than a threshold, role change can be performed even the channel quality of PCell is better than PSCell. It may cause ping-pong and waste resources for signaling.

Moreover, there is no event which can compare the PCell and PSCell. So, if once the target cell is added as PSCell, it would be hard to compare the channel quality of source cell (i.e., PCell) and target cell (i.e., PSCell).

In legacy handover, UE reports measurement reports and receives handover command when source cell decides to handover. However, in DC based handover, UE receives SCG addition at first and UE receives role change request via the next RRC connection reconfiguration message. Likewise, the MgNB sends/receives SgNB addition/acknowledge message to/from the target cell and MgNB sends/receives Role Change Request to/from SgNB. Therefore, the DC based handover can cause delayed handover due to multiple handshakes between the source gNB and target gNB.

The conditional handover is considered to reduce the latency during the handover. If DC based handover is combined with conditional handover, the number of handshakes between the gNBs can be reduced and handover failure can be reduced. For example, UE reports measurement reports when the target cell is better than a threshold. The source cell adds the target cell as the SgNB and prepares the role change simultaneously when channel quality of the source cell is still in good condition. After that UE receives role change trigger condition (e.g., PSCell is better than PCell) and triggers the role change when it is satisfied. The gNBs can change the role immediately because gNBs prepared the role change in advanced. It can reduce the role change latency and handover/role change failure could be reduced.

Reconfiguration with sync is described. Section 5.3.5.5.2 and Section 5.3.5.8 of 3GPP TS 38.331 V15.4.0 (2018-12) can be referred.

The UE shall perform the following actions to execute a reconfiguration with sync.

-   -   1> if the security is not activated, perform the actions upon         going to RRC_IDLE with the release cause ‘other’ upon which the         procedure ends;     -   1> stop timer T310 for the corresponding SpCell, if running;     -   1> start timer T304 for the corresponding SpCell with the timer         value set to t304, as included in the reconfigurationWithSync;     -   1> if thefrequencyInfoDL is included:     -   2> consider the target SpCell to be one on the SSB frequency         indicated by the frequencyInfoDL with a physical cell identity         indicated by the physCellId;     -   1> else:     -   2> consider the target SpCell to be one on the SSB frequency of         the source SpCell with a physical cell identity indicated by the         physCellId;     -   1> start synchronising to the DL of the target SpCell;     -   1> apply the specified BCCH configuration;     -   1> acquire the MIB;     -   1> reset the MAC entity of this cell group;     -   1> consider the SCell(s) of this cell group, if configured, to         be in deactivated state;     -   1> apply the value of the newUE-Identity as the cell radio         network temporary identifier (C-RNTI) for this cell group;     -   1> configure lower layers in accordance with the received         spCellConfigCommon;     -   1> configure lower layers in accordance with any additional         fields, not covered in the previous, if included in the received         reconfigurationWithSync.

The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.

The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.

When the UE is unable to comply with RRCReconfiguration, the UE shall:

-   -   1> if the UE is operating in E-UTRAN-NR dual connectivity         (EN-DC):     -   2> if the UE is unable to comply with (part of) the         configuration included in the RRCReconfiguration message         received over SRB3;     -   3> continue using the configuration used prior to the reception         of RRCReconfiguration message;     -   3> initiate the SCG failure information procedure to report SCG         reconfiguration error, upon which the connection reconfiguration         procedure ends;     -   2> else, if the UE is unable to comply with (part of) the         configuration included in the RRCReconfiguration message         received over SRB1;     -   3> continue using the configuration used prior to the reception         of RRCReconfiguration message;     -   3> initiate the connection re-establishment procedure, upon         which the connection reconfiguration procedure ends.     -   1> else if RRCReconfiguration is received via NR:     -   2> if the UE is unable to comply with (part of) the         configuration included in the RRCReconfiguration message;     -   3> continue using the configuration used prior to the reception         of RRCReconfiguration message;     -   3> if security has not been activated:     -   4> perform the actions upon going to RRC_IDLE, with release         cause ‘other’     -   3> else if AS security has been activated but SRB2 and at least         one DRB have not been setup:     -   4> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’;     -   3> else:     -   4> initiate the connection re-establishment procedure, upon         which the reconfiguration procedure ends;     -   1> else if RRCReconfiguration is received via other RAT         (handover to NR failure):     -   2> if the UE is unable to comply with any part of the         configuration included in the RRCReconfiguration message:     -   3> perform the actions defined for this failure case applicable         for the other RAT.

The UE may apply above failure handling also in case the RRCReconfiguration message causes a protocol error for which the generic error handling specifies that the UE shall ignore the message.

If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e., there is no partial success/failure.

Upon T304 expiry (i.e., reconfiguration with sync failure), the UE shall:

-   -   1> if T304 of the MCG expires:     -   2> release dedicated preambles provided in rach-ConfigDedicated         if configured;     -   2> revert back to the UE configuration (which may include state         variables and parameters of each radio bearer) used in the         source PCell;     -   2> initiate the connection re-establishment procedure.     -   1> else if T304 of a secondary cell group expires:     -   2> release dedicated preambles provided in rach-ConfigDedicated,         if configured;     -   2> initiate the SCG failure information procedure to report SCG         reconfiguration with sync failure, upon which the RRC         reconfiguration procedure ends;     -   1> else if T304 expires when RRCReconfiguration is received via         other RAT (handover to NR failure):     -   2> reset MAC;     -   2> perform the actions defined for this failure case applicable         for the other RAT.

Radio link failure is described. Section 5.3.10 of 3GPP TS 38.331 V15.4.0 (2018-12) can be referred.

For detection of physical layer problems in RRC_CONNECTED, the UE shall:

-   -   1> upon receiving N310 consecutive “out-of-sync” indications for         the SpCell from lower layers while neither T300, T301, T304,         T311 nor T319 are running:     -   2> start timer T310 for the corresponding SpCell.

For recovery of physical layer problems, upon receiving N311 consecutive “in-sync” indications for the SpCell from lower layers while T310 is running, the UE shall:

-   -   1> stop timer T310 for the corresponding SpCell.

In this case, the UE maintains the RRC connection without explicit signalling, i.e., the UE maintains the entire radio resource configuration.

Periods in time where neither “in-sync” nor “out-of-sync” is reported by layer 1 do not affect the evaluation of the number of consecutive “in-sync” or “out-of-sync” indications.

For detection of radio link failure, the UE shall:

-   -   1> upon T310 expiry in PCell; or     -   1> upon random access problem indication from MCG MAC while         neither T300, T301, T304, T311 nor T319 are running; or     -   1> upon indication from MCG RLC that the maximum number of         retransmissions has been reached:     -   2> if CA duplication is configured and activated; and for the         corresponding logical channel allowedServingCells only includes         SCell(s):     -   3> initiate the failure information procedure to report RLC         failure.     -   2> else:     -   3> consider radio link failure to be detected for the MCG, i.e.,         RLF;     -   3> if AS security has not been activated:     -   4> perform the actions upon going to RRC_IDLE, with release         cause ‘other’;     -   3> else if AS security has been activated but SRB2 and at least         one DRB have not been setup:     -   4> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’;     -   3> else:     -   4> initiate the connection re-establishment procedure.

The UE shall:

-   -   1> upon T310 expiry in PSCell; or     -   1> upon random access problem indication from SCG MAC; or     -   1> upon indication from SCG RLC that the maximum number of         retransmissions has been reached:     -   2> if CA duplication is configured and activated; and for the         corresponding logical channel allowedServingCells only includes         SCell(s):     -   3> initiate the failure information procedure to report RLC         failure.     -   2> else:     -   3> consider radio link failure to be detected for the SCG, i.e.,         SCG-RLF;     -   3> initiate the SCG failure information procedure to report SCG         radio link failure.

RRC connection re-establishment is described. Section 5.3.7 of 3GPP TS 38.331 V15.4.0 (2018-12) can be referred.

The purpose of this procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED, for which security has been activated with SRB2 and at least one DRB setup, may initiate the procedure in order to continue the RRC connection. The connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network responds with an RRCSetup. If AS security has not been activated, the UE does not initiate the procedure but instead moves to RRC_IDLE directly, with release cause ‘other’. If AS security has been activated, but SRB2 and at least one DRB are not setup, the UE does not initiate the procedure but instead moves to RRC_IDLE directly, with release cause ‘RRC connection failure’.

The network applies the procedure as follows:

-   -   > When AS security has been activated and the network retrieves         or verifies the UE context:     -   >> to re-activate AS security without changing algorithms;     -   >> to re-establish and resume the SRB1;     -   > When UE is re-establishing an RRC connection, and the network         is not able to retrieve or verify the UE context:     -   >> to discard the stored AS Context and release all RB;     -   >> fallback to establish a new RRC connection.

The UE initiates the procedure when one of the following conditions is met: 1> upon detecting radio link failure of the MCG; or

-   -   1> upon re-configuration with sync failure of the MCG; or     -   1> upon mobility from NR failure; or     -   1> upon integrity check failure indication from lower layers         concerning SRB1 or SRB2, except if the integrity check failure         is detected on the RRCReestablishment message; or     -   1> upon an RRC connection reconfiguration failure.

Upon initiation of the procedure, the UE shall:

-   -   1> stop timer T310, if running;     -   1> stop timer T304, if running;     -   1> start timer T311;     -   1> suspend all RBs, except SRB0;     -   1> reset MAC;     -   1> release the MCG SCell(s), if configured;     -   1> release the current dedicated ServingCell configuration;     -   1> release delayBudgetReportingConfig, if configured, and stop         timer T342, if running;     -   1> release overheatingAssistanceConfig, if configured and stop         timer T345, if running;     -   1> perform cell selection in accordance with the cell selection         process which will be described below in detail.

Upon selecting a suitable NR cell, the UE shall:

-   -   1> ensure having valid and up to date essential system         information;     -   1> stop timer T311;     -   1> start timer T301;     -   1> if T390 is running:     -   2> stop timer T390 for all access categories;     -   2> perform the actions for barring alleviation;     -   1> apply the default L1 parameter values as specified in         corresponding physical layer specifications except for the         parameters for which values are provided in SIB1;     -   1> apply the default MAC Cell Group configuration;     -   1> apply the timeAlignmentTimerCommon included in SIB1;     -   1> initiate transmission of the RRCReestablishmentRequest         message; This procedure applies also if the UE returns to the         source PCell.

Upon initiating an inter-RAT cell, the UE shall:

-   -   1> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’.

The UE shall set the contents of RRCReestablishmentRequest message as follows:

-   -   1> set the ue-Identity as follows:     -   2> set the c-RNTI to the cell radio network temporary identity         (C-RNTI) used in the source PCell (reconfiguration with sync or         mobility from NR failure) or used in the PCell in which the         trigger for the re-establishment occurred (other cases);     -   2> set the physCellId to the physical cell identity of the         source PCell (reconfiguration with sync or mobility from NR         failure) or of the PCell in which the trigger for the         re-establishment occurred (other cases);     -   2> set the shortMAC-I to the 16 least significant bits of the         MAC-I calculated:     -   3> over the ASN.1 encoded (i.e., a multiple of 8 bits)         VarShortMAC-Input;     -   3> with the K_(RRCint) key and integrity protection algorithm         that was used in the source PCell (reconfiguration with sync or         mobility from NR failure) or of the PCell in which the trigger         for the re-establishment occurred (other cases); and     -   3> with all input bits for COUNT, BEARER and DIRECTION set to         binary ones;     -   1> set the reestablishmentCause as follows:     -   2> if the re-establishment procedure was initiated due to         reconfiguration failure:     -   3> set the reestablishmentCause to the value         reconfigurationFailure;     -   2> else if the re-establishment procedure was initiated due to         reconfiguration with sync failure (intra-NR handover failure or         inter-RAT mobility from NR failure):     -   3> set the reestablishmentCause to the value handoverFailure;     -   2> else:     -   3> set the reestablishmentCause to the value otherFailure;     -   1> re-establish PDCP for SRB1;     -   1> re-establish RLC for SRB1;     -   1> apply the specified configuration for SRB1;     -   1> configure lower layers to suspend integrity protection and         ciphering for SRB1;     -   Ciphering is not applied for the subsequent RRCReestablishment         message used to resume the connection. An integrity check is         performed by lower layers, but merely upon request from RRC.     -   1> resume SRB1;     -   1> submit the RRCReestablishmentRequest message to lower layers         for transmission.

Upon receiving of the RRCReestablishment by the UE, the UE shall:

-   -   1> stop timer T301;     -   1> consider the current cell to be the PCell;     -   1> store the nextHopChainingCount value indicated in the         RRCReestablishment message;     -   1> update the K_(gNB) key based on the current K_(gNB) or the         NH, using the stored nextHopChainingCount value;     -   1> derive K_(RRCenc) and K_(UPenc) key associated with the         previously configured cipheringAlgorithm;     -   1> derive the K_(RRCint) and K_(UPint) key associated with the         previously configured integrityProtAlgorithm.     -   1> request lower layers to verify the integrity protection of         the RRCReestablishment message, using the previously configured         algorithm and the K_(RRCint) key;     -   1> if the integrity protection check of the RRCReestablishment         message fails:     -   2> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’, upon which the procedure ends;     -   1> configure lower layers to resume integrity protection for         SRB1 using the previously configured algorithm and the         K_(RRCint) key immediately, i.e., integrity protection shall be         applied to all subsequent messages received and sent by the UE,         including the message used to indicate the successful completion         of the procedure;     -   1> configure lower layers to resume ciphering for SRB1 using the         previously configured algorithm and, the K_(RRCenc) key         immediately, i.e., ciphering shall be applied to all subsequent         messages received and sent by the UE, including the message used         to indicate the successful completion of the procedure;     -   1> release the measurement gap configuration indicated by the         measGapConfig, if configured;     -   1> submit the RRCReestablishmentComplete message to lower layers         for transmission;     -   1> the procedure ends.

Upon T311 expiry, the UE shall:

-   -   1> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’.

The UE shall:

-   -   1> if timer T301 expires; or     -   1> if the selected cell becomes no longer suitable according to         the cell selection criteria:     -   2> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’.

Upon reception of the RRCSetup by the UE, the UE shall:

-   -   1> perform the RRC connection establishment procedure.

Cell selection is described. Sections 5.2.3 and 5.2.6 of 3GPP TS 38.304 V15.2.0 (2018-12) can be referred.

Cell selection is performed by one of the following two procedures:

-   -   a) Initial cell selection (no prior knowledge of which RF         channels are NR frequencies):     -   1. The UE shall scan all RF channels in the NR bands according         to its capabilities to find a suitable cell.     -   2. On each frequency, the UE need only search for the strongest         cell.     -   3. Once a suitable cell is found, this cell shall be selected.     -   b) Cell selection by leveraging stored information:     -   1. This procedure requires stored information of frequencies and         optionally also information on cell parameters from previously         received measurement control information elements or from         previously detected cells.     -   2. Once the UE has found a suitable cell, the UE shall select         it.     -   3. If no suitable cell is found, the initial cell selection         procedure in a) shall be started.

Priorities between different frequencies or RATs provided to the UE by system information or dedicated signaling are not used in the cell selection process.

The cell selection criterion S is fulfilled when:

-   -   Srxlev>0 AND Squal>0     -   where:

Srxlev=Q _(rxlevmeas)−(Q _(rxlevmin) +Q _(rxlevminoffset))−P _(compensation) −Qoffset_(temp)

Squal=Q _(qualmeas)−(Q _(qualmin) +Q _(qualminoffset))−Qoffset_(temp)

Table 7 shows parameters for the cell selection criterion S.

TABLE 7 Srxlev Cell selection RX level value (dB) Squal Cell selection quality value (dB) Qoffset_(temp) Offset temporarily applied to a cell (dB) Q_(rxlevmeas) Measured cell RX level value (RSRP) Q_(qualmeas) Measured cell quality value (RSRQ) Q_(rxlevmin) Minimum required RX level in the cell (dBm). If the UE supports SUL frequency for this cell, Qrxlevmin is obtained from RxLevMinSUL, if present, in SIB1, SIB2 and SIB4, additionally, if Q_(rxlevminoffsetcellSUL) is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell; else Qrxlevmin is obtained from q-RxLevMin in SIB1 SIB1, SIB2 and SIB4, additionally, if Q_(rxlevminoffsetcell) is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell. Q_(qualmin) Minimum required quality level in the cell (dB). Additionally, if Q_(qualminoffsetcell) is signalled for the concerned cell, this cell specific offset is added to achieve the required minimum quality level in the concerned cell. Q_(rxlevminoffset) Offset to the signalled Q_(rxlevmin) taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN. Q_(qualminoffset) Offset to the signalled Q_(qualmin) taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN. P_(compensation) If the UE supports the additionalPmax in the NR-NS-PmaxList, if present, in SIB1, SIB2 and SIB4: max(P_(EMAX1) − P_(PowerClass), 0) − (min(P_(EMAX2), P_(PowerClass)) − min(P_(EMAX1), P_(PowerClass))) (dB); else: max(P_(EMAX1) − P_(PowerClass), 0) (dB) P_(EMAX1), P_(EMAX2) Maximum TX power level of a UE may use when transmitting on the uplink in the cell (dBm) defined as P_(EMAX). If UE supports SUL frequency for this cell, P_(EMAX1) and P_(EMAX2) are obtained from the p- Max for SUL in SIB1 and NR-NS-PmaxList for SUL respectively in SIB1, SIB2 and SIB4, else P_(EMAX1) and P_(EMAX2) are obtained from the p-Max and NR-NS-PmaxList respectively in SIB1, SIB2 and SIB4 for regular UL. P_(PowerClass) Maximum RF output power of the UE (dBm) according to the UE power class.

The signaled values Q_(rxlevminoffset) and Q_(qualminoffset) are only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN. During this periodic search for higher priority PLMN, the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN.

At reception of RRCRelease message to transition the UE to RRC_IDLE or RRC_INACTIVE, UE shall attempt to camp on a suitable cell according to redirectedCarrierInfo if included in the RRCRelease message. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease message does not contain the redirectedCarrierInfo, UE shall attempt to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to find a suitable cell to camp on.

When returning to RRC_IDLE state after UE moved to RRC_CONNECTED state from camped on any cell state, UE shall attempt to camp on an acceptable cell according to redirectedCarrierInfo, if included in the RRCRelease message. If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the RRCRelease message does not contain redirectedCarrierInfo UE shall attempt to select an acceptable cell on an NR frequency. If no acceptable cell is found according to the above, the UE shall continue to search for an acceptable cell of any PLMN in state any cell selection.

Event A3 (Neighbor becomes offset better than SpCell) is described. Section 5.5.4.4 of 3GPP TS 38.331 V15.4.0 (2018-12) can be referred.

The UE shall:

-   -   1> consider the entering condition for this event to be         satisfied when condition A3-1, as specified below, is fulfilled;     -   1> consider the leaving condition for this event to be satisfied         when condition A3-2, as specified below, is fulfilled;     -   1> use the SpCell for Mp, Ofp and Ocp.     -   Inequality A3-1 (Entering condition)     -   Mn+Ofn+Ocn−Hys> Mp+Ofp+Ocp+Off     -   Inequality A3-2 (Leaving condition)     -   Mn+Ofn+Ocn+Hys<Mp+Ofp+Ocp+Off

The variables in the formula are defined as follows:

-   -   Mn is the measurement result of the neighbouring cell, not         taking into account any offsets.     -   Ofn is the measurement object specific offset of the reference         signal of the neighbour cell (i.e. offsetMO as defined within         measObjectNR corresponding to the neighbour cell).     -   Ocn is the cell specific offset of the neighbour cell (i.e.,         celllndividualOffset as defined within measObjectNR         corresponding to the frequency of the neighbour cell), and set         to zero if not configured for the neighbour cell.     -   Mp is the measurement result of the SpCell, not taking into         account any offsets.     -   Ofp is the measurement object specific offset of the SpCell         (i.e. offsetMO as defined within measObjectNR corresponding to         the SpCell).     -   Ocp is the cell specific offset of the SpCell (i.e.,         celllndividualOffset as defined within measObjectNR         corresponding to the SpCell), and is set to zero if not         configured for the SpCell.     -   Hys is the hysteresis parameter for this event (i.e., hysteresis         as defined within reportConfigNR for this event).     -   Off is the offset parameter for this event (i.e., a3-Offset as         defined within reportConfigNR for this event).     -   Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of         RSRQ and reference signal (RS) signal to interference plus noise         ratio (SINR).     -   Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

Event A5 (SpCell becomes worse than threshold1 and neighbor becomes better than threshold2) is described. Section 5.5.4.6 of 3GPP TS 38.331 V15.4.0 (2018-12) can be referred.

The UE shall:

-   -   1> consider the entering condition for this event to be         satisfied when both condition A5-1 and condition A5-2, as         specified below, are fulfilled;     -   1> consider the leaving condition for this event to be satisfied         when condition A5-3 or condition A5-4, i.e. at least one of the         two, as specified below, is fulfilled;     -   1> use the SpCell for Mp.     -   Inequality A5-1 (Entering condition 1)     -   Mp+Hys<Thresh1     -   Inequality A5-2 (Entering condition 2)     -   Mn+Ofn+Ocn−Hys> Thresh2     -   Inequality A5-3 (Leaving condition 1)     -   Mp−Hys> Thresh1     -   Inequality A5-4 (Leaving condition 2)     -   Mn+Ofn+Ocn+Hys<Thresh2

The variables in the formula are defined as follows:

-   -   Mp is the measurement result of the NR SpCell, not taking into         account any offsets.     -   Mn is the measurement result of the neighbouring cell, not         taking into account any offsets.     -   Ofn is the measurement object specific offset of the neighbour         cell (i.e., offsetMO as defined within measObjectNR         corresponding to the neighbour cell).     -   Ocn is the cell specific offset of the neighbour cell (i.e.,         celllndividualOffset as defined within measObjectNR         corresponding to the neighbour cell), and set to zero if not         configured for the neighbour cell.     -   Hys is the hysteresis parameter for this event (i.e., hysteresis         as defined within reportConfigNR for this event).     -   Thresh1 is the threshold parameter for this event (i.e.,         a5-Threshold1 as defined within reportConfigNR for this event).     -   Thresh2 is the threshold parameter for this event (i.e.,         a5-Threshold2 as defined within reportConfigNR for this event).     -   Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of         RSRQ and RS-SINR.     -   Ofn, Ocn, Hys are expressed in dB.     -   Threshlis expressed in the same unit as Mp.     -   Thresh2 is expressed in the same unit as Mn.

Even though some conditional mobility have been configured properly, radio link problem on the serving cell may suddenly happen based on radio link monitoring (RLM). In this case, the UE may not trigger the configured conditional mobility, because radio resource management (RRM) measurement results of the serving cell is still good and/or target cell quality is not yet very high enough to perform conditional mobility.

However, if the radio link problem is detected from the serving cell, even though the target cell quality is not very good, but if the target cell quality is merely suitable for mobility, it may be better to perform the mobility to change the serving cell to the target cell. If not, the UE may undergo the service interruption due to the radio link problem on the serving cell.

According to implementations of the present disclosure, for a UE which has been configured with the conditional mobility, when the UE detects a serving cell problem, the UE may relax the mobility condition related to the corresponding serving cell so that the mobility can be performed more easily.

Implementations of the present disclosure can be applied to conditional mobility, in which one or more candidate cells are determined based on condition first, and actual mobility is performed towards one of the candidate cells. The conditional mobility may include conditional handover, conditional DC based handover, and/or conditional SCG change, etc.

The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals/messages/fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings.

FIG. 18 shows an example of a method for a wireless device to which implementations of the present disclosure is applied.

In some implementations, the wireless device may be in communication with at least one of a mobile device, a network, and/or autonomous vehicles other than the wireless device.

In step S1800, the wireless device receives information for a conditional mobility condition related to a target cell.

In some implementations, the conditional mobility condition may be configured by comparison between the measurement result of the target cell and a measurement result of the serving cell. For example, the conditional mobility condition may be that the measurement result of the target cell is better than the measurement result of the serving cell by an offset.

For example, the conditional mobility condition may be event A3.

In some implementations, the conditional mobility condition may include a first part related to the serving cell with a first threshold and a second part related to the target cell with a second threshold. For example, the conditional mobility condition may be event A5.

In some implementations, the conditional mobility condition may be configured by a threshold for the target cell.

In some implementations, the information for the conditional mobility condition related to the target cell may be received via a conditional mobility configuration. The conditional mobility configuration may include a list of candidate target cells including the target cell. For example, the list of candidate target cells may include an ID of the candidate target cells. The conditional mobility configuration may include an ID of the serving cell and/or type of the conditional mobility.

In step S1810, the wireless device detects a radio link problem on a serving cell.

In some implementations, the radio link problem may be detected upon expiry of a timer, which starts to running upon receiving N-consecutive out-of-sync indications for the serving cell from lower layers.

In some implementations, the radio link problem may be detected upon receiving a random access problem indication from MCG MAC.

In some implementations, the radio link problem may be detected upon receiving an indication from MCG RLC that a maximum number of retransmissions has been reached.

In some implementations, the radio link problem may be detected upon receiving N-consecutive out-of-sync indications for the serving cell from lower layers,

In some implementations, the radio link problem may be detected upon receiving a random access problem indication from SCG MAC.

In some implementations, the radio link problem may be detected upon receiving an indication from SCG RLC that a maximum number of retransmissions has been reached.

In some implementations, the radio link problem may be detected upon re-configuration with sync failure of a MCG.

In some implementations, the radio link problem may be detected upon re-configuration with sync failure of a SCG.

In some implementations, the radio link problem may be detected upon receiving an integrity check failure indication from lower layers regarding SRB1 and/or SRB2.

In some implementations, the radio link problem may be detected upon RRC connection reconfiguration failure.

In some implementations, the serving cell may be a PCell.

In step S1820, the wireless device performs a conditional mobility to the target cell by using a mobility condition related to the target cell upon detecting the radio link problem on the serving cell.

In some implementations, the mobility condition may correspond to a satisfaction of a cell selection criterion. The satisfaction of the cell selection criterion may correspond to that a measurement result of the target cell is above a default threshold.

For example, the wireless device may perform the conditional mobility to the target cell upon that (e.g., when) a cell selection criterion S is satisfied, e.g., the measurement result of the target cell is above the default threshold, regardless of a quality of the serving cell, e.g., PCell. In other words, the conditional mobility condition may be ignored, but nevertheless the conditional mobility can be performed by using a cell selection criterion S.

For example, the target cell may be a suitable cell upon cell selection.

In some implementations, the conditional mobility may include a conditional serving cell change, a conditional serving cell addition and/or a conditional serving cell release.

FIG. 19 show an example of a method for UE to perform conditional mobility to which implementations of the present disclosure is applied.

In step S1900, the UE establishes a connection with gNB.

In some implementations, the UE may perform initial access towards a cell. The UE and the cell may perform RACH procedure. The cell may become a serving cell.

In some implementations, the UE may establish or resume a connection with the gNB and enters RRC_CONNECTED.

In some implementations, the UE may perform AS security activation upon receiving Security Mode Command from the gNB.

In some implementations, the UE may configure radio bearers and radio configuration upon receiving RRC reconfiguration or resumes radio bearers and radio configuration upon receiving RRC resume.

In step S1910, the UE receives a conditional mobility configuration.

In some implementations, the conditional mobility configuration may include a list which consists of one or more candidate cells. For example, the list may include ID of the one or more candidate cells).

In some implementations, the conditional mobility configuration may include the mobility condition for one or more candidate cells. The mobility condition may be configured in various forms as follows: For example, the mobility condition may be configured by comparison between neighbor cell and serving cell. For example, the mobility condition may be event A3, i.e., neighbor becomes offset better than SpCell.

For example, the mobility condition may be configured by a first part related to the serving cell and a second part related to the neighbor cell. For example, the first part related to the serving cell may be a first condition with threshold 1 for the serving cell, and the second part related to the neighbor cell may be a second condition with threshold 2 for the neighbor cell. For example, the mobility condition may be event A5, i.e., SpCell becomes worse than threshold1 and neighbor becomes better than threshold2.

For example, the mobility condition may be configured by including a threshold for neighbor cell.

In some implementations, the conditional mobility configuration may further include the source cell identity and/or the type of mobility.

In some implementations, the conditional mobility configuration may be provided by RRC dedicated signaling and/or broadcast information such as system information.

In step S1920, the UE detects a serving cell problem. When at least one of the following events occur, the UE may consider the serving cell problem is detected.

1) Upon receiving N-consecutive “out-of-sync” indications for a serving cell from lower layers, e.g., physical layer, the UE may consider the serving cell problem is detected for the serving cell. N may be a constant and can be set to 1.

2) Upon receiving N-consecutive “out-of-sync” indications for a serving cell from lower layers, the UE may start a timer. When the timer expires, the UE may consider the serving cell problem is detected for the serving cell.

3) Upon random access problem indication from MCG MAC, the UE may consider the serving cell problem is detected for PCell.

4) Upon random access problem indication from SCG MAC, the UE may consider the serving cell problem is detected for PSCell.

5) Upon indication from MCG RLC that the maximum number of retransmissions has been reached, the UE may consider the serving cell problem is detected for PCell.

6) Upon indication from SCG RLC that the maximum number of retransmissions has been reached, the UE may consider the serving cell problem is detected for PSCell.

7) Upon re-configuration with sync failure of the MCG, the UE may consider the serving cell problem is detected for PCell.

8) Upon re-configuration with sync failure of the SCG, the UE consider the serving cell problem is detected for PSCell.

9) Upon integrity check failure indication from lower layers concerning SRB1 or SRB2, the UE may consider the serving cell problem is detected for PCell.

10) Upon an RRC connection reconfiguration failure, the UE may consider the serving cell problem is detected for PCell.

In step S1930, the UE relaxes the mobility condition. Examples of how to relax the mobility condition are described below. The relaxation of the mobility condition may depend on how the mobility condition is configured.

1) In some implementations, if the mobility condition is configured by comparison between neighbor cell and serving cell, e.g., event A3, the UE may change the mobility condition to the form of comparison between neighbor cell and a default threshold.

For example, for PCell change, e.g., handover, a configured mobility condition may be ‘Neighbor becomes better than PCell’ and/or ‘Neighbor becomes offset better than SpCell’. When the UE detects the serving cell problem for PCell, the UE may relax the mobility condition by changing the mobility condition to ‘Neighbor becomes better than default threshold’. This means that the UE can perform the PCell change if neighbor becomes better than the default threshold, regardless of PCell quality.

2) In some implementations, if configured mobility condition is composed of the first part related to the serving cell and second part related to the neighbor cell, e.g., event A5, the UE may remove the first part from the configured mobility condition.

For example, for PCell change, e.g., handover, a configured mobility condition may be ‘PCell becomes worse than threshold 1 and neighbor becomes better than threshold 2’. When the UE detects the serving cell problem for PCell, the UE may relax the mobility condition by removing the first part from the mobility condition. That is, the relaxed mobility condition may be “neighbor becomes better than threshold 2”. That is, the UE can perform the PCell change if neighbor becomes better than threshold2, regardless of measurement results of the PCell.

3) In some implementations, if configured mobility condition includes a threshold for neighbor cell, the UE may scale down the threshold related to the neighbor cell.

For example, for PSCell change, a configured mobility condition may be ‘neighbor becomes better than a threshold’. When the UE detects the serving cell problem for PSCell, the UE may relax the mobility condition by scaling down the threshold. This means that the UE can perform the PSCell change if neighbor becomes better than scaled down threshold, i.e., lower threshold.

4) In some implementations, the UE may ignore the configured mobility condition and perform the mobility related to the serving cell, if the target cell satisfies the minimum requirement.

For example, the minimum requirement may be ‘the neighbor cell quality is higher than a default threshold.’ Or, cell selection criterion (criterion S) may also be used as the minimum requirement. That is, when the UE detects a serving cell problem and the target cell satisfies the minimum requirement, the UE can perform the corresponding mobility to the target cell.

For example, if the mobility condition is configured by comparison between neighbor cell and serving cell, e.g., event A3, the UE may use another mobility condition rather than the mobility condition configured by the conditional mobility. Another mobility condition may correspond to the minimum requirement.

For example, for PCell change, e.g., handover, a configured mobility condition may be ‘Neighbor becomes better than PCell’ and/or ‘Neighbor becomes offset better than SpCell’. When the UE detects the serving cell problem for PCell, the UE may ignore the configured mobility condition and use the minimum requirement ‘the neighbor cell quality is higher than a default threshold’ to perform mobility to the target cell. This means that the UE can perform the PCell change if the neighbor cell quality becomes better than the default threshold, regardless of PCell quality.

Each option for relaxation of the mobility condition described above may be applied independently. Or, each option for relaxation of the mobility condition described above may be used with other options.

In step S1940, for the UE which has been configured with the conditional mobility, the UE performs the mobility to the target cell, if the mobility condition is met.

In some implementations, the mobility may include at least one of (conditional) serving cell change, (conditional) cell addition, and/or (conditional) cell release.

An example of UE operations according to implementations of the present disclosure is as follows.

1) The UE receives a conditional mobility configuration from network. The source cell of mobility is a PCell and a target cell of mobility is a neighbor cell C, respectively. The type of mobility is set to handover. The mobility condition is ‘Neighbor becomes offset better than PCell’, e.g., Event A3.

2) The UE receives N-consecutive out-of-sync indications from physical layer. Then, the UE may apply the relaxed mobility condition that ‘Neighbor becomes better than default threshold’, instead of configured mobility condition. Or, the UE may ignore the configured mobility condition, and use the minimum requirement that ‘Neighbor becomes better than default threshold’.

3) The measurement results of the target cell, i.e., cell C, already satisfies the relaxed mobility condition and/or minimum requirement. So, the UE immediately performs the handover to the cell C.

An example of UE operations according to implementations of the present disclosure is as follows.

Upon selecting a suitable NR cell, the UE shall:

-   -   1> ensure having valid and up to date essential system         information;     -   1> stop timer T311;     -   1> if T390 is running:     -   2> stop timer T390 for all access categories;     -   2> perform the actions regarding barring alleviation;     -   1> if attemptCHO is configured; and     -   1> if the selected cell is one of the candidate cells in         VarCHO-Config:     -   2> apply the stored cho-RRCReconfig associated to the selected         cell;     -   2> remove all the entries within VarCHO-Config, if any;     -   2> perform the actions regarding reception of an         RRCReconfiguration by the UE (i.e., perform conditional         handover);     -   1> else:     -   2> remove all the entries within VarCHO-Config, if any;     -   2> start timer T301; 2> apply the default L1 parameter values as         specified in corresponding physical layer specifications except         for the parameters for which values are provided in SIB1;     -   2> apply the default MAC Cell Group configuration;     -   2> apply the CCCH configuration;     -   2> apply the timeAlignmentTimerCommon included in SIB1;     -   2> initiate transmission of the RRCReestablishmentRequest         message;

This procedure applies also if the UE returns to the source PCell.

Upon selecting an inter-RAT cell, the UE shall:

-   -   1> perform the actions upon going to RRC_IDLE, with release         cause ‘RRC connection failure’.

In other words, if attemptCHO is present in the CHO-Config information element (IE), the UE shall perform conditional handover if selected cell is a conditional handover candidate cell while timer T311 is running.

The present disclosure can have various advantageous effects.

For example, the wireless device can autonomously change a serving cell as soon as a problem happens in the serving cell if there is a suitable target cell.

For example, if a target cell is configured for conditional mobility, upon detecting a problem on the serving cell, the wireless device can autonomously change a serving cell enough that the target cell is suitable upon cell selection.

For example, if the radio link problem is detected from a serving cell, even though the target cell quality is not very good, but if the target cell quality is suitable for mobility, mobility to the target cell can be performed regardless of the serving cell quality.

For example, the wireless device can avoid radio link failure and continue data transmission/reception without any interruption.

Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims. 

1-15. (canceled)
 16. A method performed by a User Equipment (UE) adapted to operate in a wireless communication system, the method comprising: receiving, from a network, a Conditional Handover (CHO) configuration including one or more conditions of one or more candidate cells, wherein the one or more conditions are based on any one of i) a first event in which a candidate cell becomes amount of an offset better than the serving cell, or i) a second event in which the serving cell becomes worse than a first threshold and a candidate cell becomes better than a second threshold, wherein the CHO configuration includes one or more configurations of each of the one or more candidate cells; evaluating the one or more conditions of each of the one or more candidate cells; considering the first event or the second event to be not fulfilled; detecting a radio link failure upon expiry of a timer in the serving cell, wherein the timer starts upon receiving N number of consecutive out-of-sync indications for the serving cell from lower layers; performing a cell selection; and i) if the cell selection is triggered by detecting the radio link failure, and ii) if a selected cell is one of the one or more candidate cells, applying a configuration associated to the selected cell, wherein the selected cell is selected based on fulfilling a cell selection criterion S, wherein the cell selection criterion S is different from the one or more conditions, and wherein the cell selection criterion S is fulfilled when: Srxlev>0 AND Squal>0 where: Srxlev=Q _(rxlevmeas)−(Q _(rxlevmin) +Q _(rxlevminoffset))−P _(compensation) −Qoffset_(temp) Squal=Q _(qualmeas)−(Q _(qualmin) +Q _(qualminoffset))−Qoffset_(temp) where: Srxlev denotes a cell selection reception (RX) level value, Q_(rxlevmeas) denotes a measured cell RX level value, Q_(rxlevmin) in denotes a minimum required RX level value in a cell, Q_(rxlevminoffset) denotes an offset to the Q_(rxlevmin), P_(compensation) denotes a parameter related to additionalPmax, Qoffset_(temp) denotes an offset temporarily applied to the cell, Squal denotes a cell selection quality value, Q_(qualmeas) denotes a measured cell quality value, Q_(qualmin) denotes a minimum required quality level value in the cell, and Q_(qualminoffset) denotes an offset to the Q_(qualmin).
 17. The method of claim 16, wherein the serving cell is a primary cell (PCell).
 18. The method of claim 16, wherein the first event is an event A3.
 19. The method of claim 16, wherein the second event is an event A5.
 20. The method of claim 16, wherein the configuration associated to the selected cell is applied regardless of a quality of the serving cell.
 21. A wireless device adapted to operate in a wireless communication system, the wireless device comprising: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, performs operations comprising: receiving, from a network via the at least one processor, a Conditional Handover (CHO) configuration including one or more conditions of one or more candidate cells, wherein the one or more conditions are based on any one of i) a first event in which a candidate cell becomes amount of an offset better than the serving cell, or i) a second event in which the serving cell becomes worse than a first threshold and a candidate cell becomes better than a second threshold, wherein the CHO configuration includes one or more configurations of each of the one or more candidate cells; evaluating the one or more conditions of each of the one or more candidate cells; considering the first event or the second event to be not fulfilled; detecting a radio link failure upon expiry of a timer in the serving cell, wherein the timer starts upon receiving N number of consecutive out-of-sync indications for the serving cell from lower layers; performing a cell selection; and i) if the cell selection is triggered by detecting the radio link failure, and ii) if a selected cell is one of the one or more candidate cells, applying a configuration associated to the selected cell, wherein the selected cell is selected based on fulfilling a cell selection criterion S, wherein the cell selection criterion S is different from the one or more conditions, and wherein the cell selection criterion S is fulfilled when: Srxlev>0 AND Squal>0 where: Srxlev=Q _(rxlevmeas)−(Q _(rxlevmin) +Q _(rxlevminoffset))−P _(compensation) −Qoffset_(temp) Squal=Q _(qualmeas)−(Q _(qualmin) +Q _(qualminoffset))−Qoffset_(temp) where: Srxlev denotes a cell selection reception (RX) level value, Q_(rxlevmeas) denotes a measured cell RX level value, Q_(rxlevmin) in denotes a minimum required RX level value in a cell, Q_(rxlevminoffset) denotes an offset to the Q_(rxlevmin), P_(compensation) denotes a parameter related to additionalPmax, Qoffset_(temp) denotes an offset temporarily applied to the cell, Squal denotes a cell selection quality value, Q_(qualmeas) denotes a measured cell quality value, Q_(qualmin) denotes a minimum required quality level value in the cell, and Q_(qualminoffset) denotes an offset to the Q_(qualmin).
 22. The wireless device of claim 21, wherein the serving cell is a primary cell (PCell).
 23. The wireless device of claim 21, wherein the first event is an event A3.
 24. The wireless device of claim 21, wherein the second event is an event A5.
 25. The wireless device of claim 21, wherein the configuration associated to the selected cell is applied regardless of a quality of the serving cell.
 26. A processing apparatus adapted to control a wireless device in a wireless communication system, the processing apparatus comprising: at least processor; and at least one memory operably connectable to the at least one processor, wherein the at least one processor is configured to perform operations comprising: obtaining a Conditional Handover (CHO) configuration including one or more conditions of one or more candidate cells, wherein the one or more conditions are based on any one of i) a first event in which a candidate cell becomes amount of an offset better than the serving cell, or i) a second event in which the serving cell becomes worse than a first threshold and a candidate cell becomes better than a second threshold, wherein the CHO configuration includes one or more configurations of each of the one or more candidate cells; evaluating the one or more conditions of each of the one or more candidate cells; considering the first event or the second event to be not fulfilled; detecting a radio link failure upon expiry of a timer in the serving cell, wherein the timer starts upon receiving N number of consecutive out-of-sync indications for the serving cell from lower layers; performing a cell selection; and i) if the cell selection is triggered by detecting the radio link failure, and ii) if a selected cell is one of the one or more candidate cells, applying a configuration associated to the selected cell, wherein the selected cell is selected based on fulfilling a cell selection criterion S, wherein the cell selection criterion S is different from the one or more conditions, and wherein the cell selection criterion S is fulfilled when: Srxlev>0 AND Squal>0 where: Srxlev=Q _(rxlevmeas)−(Q _(rxlevmin) +Q _(rxlevminoffset))−P _(compensation) −Qoffset_(temp) Squal=Q _(qualmeas)−(Q _(qualmin) +Q _(qualminoffset))−Qoffset_(temp) where: Srxlev denotes a cell selection reception (RX) level value, Q_(rxlevmeas) denotes a measured cell RX level value, Q_(rxlevmin) in denotes a minimum required RX level value in a cell, Q_(rxlevminoffset) denotes an offset to the Q_(rxlevmin), P_(compensation) denotes a parameter related to additionalPmax, Qoffset_(temp) denotes an offset temporarily applied to the cell, Squal denotes a cell selection quality value, Q_(qualmeas) denotes a measured cell quality value, Q_(qualmin) denotes a minimum required quality level value in the cell, and Q_(qualminoffset) denotes an offset to the Q_(qualmin).
 27. The processing apparatus of claim 26, wherein the serving cell is a primary cell (PCell).
 28. The processing apparatus of claim 26, wherein the first event is an event A3.
 29. The processing apparatus of claim 26, wherein the second event is an event A5.
 30. The processing apparatus of claim 26, wherein the configuration associated to the selected cell is applied regardless of a quality of the serving cell. 